OCPBUGS-76403, CORENET-6055: [release-4.15] Dockerfile: Unpin OVN and consume the latest from FDP by igsilya · Pull Request #2974 · openshift/ovn-kubernetes

igsilya · 2026-02-09T15:14:46Z

OVN-Kubernetes is always lagging behind on the version of OVN it pins. This is causing a lot of trouble with keeping up with bug fixes and especially CVE fixes on older branches, resulting in scanners flagging this image with poor security grades and much longer time for bug fixes to be delivered to customers as the PR backporting process can take weeks or even months.

Removing the pin, so every time the new build is released in FDP, it automatically gets into versions of OpneShift that use it. There is a pre-release testing process in place between FDP and OCP QE that ensures the required test coverage before the new build is released through FDP.

This PR will bring updated OVN builds and will allow picking up newer ones automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

(cherry picked from commit 3771a89)

Manual cherry pick of the change from 4.16: #2972

openshift-ci-robot · 2026-02-09T15:14:52Z

@igsilya: This pull request references CORENET-6055 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.z" version, but no target version was set.

Details

In response to this:

OVN-Kubernetes is always lagging behind on the version of OVN it pins. This is causing a lot of trouble with keeping up with bug fixes and especially CVE fixes on older branches, resulting in scanners flagging this image with poor security grades and much longer time for bug fixes to be delivered to customers as the PR backporting process can take weeks or even months.

Removing the pin, so every time the new build is released in FDP, it automatically gets into versions of OpneShift that use it. There is a pre-release testing process in place between FDP and OCP QE that ensures the required test coverage before the new build is released through FDP.

Keeping OKD versions separate since sometimes new major versions are not released at the same time in FDP/RHEL and CentOS, so we may need them different at some point in time.

This PR will bring updated OVN builds and will allow picking up newer ones automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

(cherry picked from commit 3771a89)

Manual cherry pick of the change from 4.16: #2972

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

igsilya · 2026-02-09T15:15:23Z

/jira cherry-pick OCPBUGS-76277

openshift-ci-robot · 2026-02-09T15:15:34Z

@igsilya: Jira Issue OCPBUGS-76277 has been cloned as Jira Issue OCPBUGS-76403. Will retitle bug to link to clone.
/retitle OCPBUGS-76403: CORENET-6055: [release-4.15] Dockerfile: Unpin OVN and consume the latest from FDP

Details

In response to this:

/jira cherry-pick OCPBUGS-76277

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2026-02-09T15:15:47Z

@igsilya: This pull request references Jira Issue OCPBUGS-76403, which is invalid:

expected dependent Jira Issue OCPBUGS-76277 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

OVN-Kubernetes is always lagging behind on the version of OVN it pins. This is causing a lot of trouble with keeping up with bug fixes and especially CVE fixes on older branches, resulting in scanners flagging this image with poor security grades and much longer time for bug fixes to be delivered to customers as the PR backporting process can take weeks or even months.

Removing the pin, so every time the new build is released in FDP, it automatically gets into versions of OpneShift that use it. There is a pre-release testing process in place between FDP and OCP QE that ensures the required test coverage before the new build is released through FDP.

Keeping OKD versions separate since sometimes new major versions are not released at the same time in FDP/RHEL and CentOS, so we may need them different at some point in time.

This PR will bring updated OVN builds and will allow picking up newer ones automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

(cherry picked from commit 3771a89)

Manual cherry pick of the change from 4.16: #2972

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

igsilya · 2026-02-09T15:17:18Z

/retitle OCPBUGS-76403, CORENET-6055: [release-4.15] Dockerfile: Unpin OVN and consume the latest from FDP

igsilya · 2026-02-09T15:24:04Z

/retitle OCPBUGS-76403, CORENET-6055: [release-4.15] Dockerfile: Unpin OVN and consume the latest from FDP

openshift-ci-robot · 2026-02-09T15:24:18Z

@igsilya: This pull request references Jira Issue OCPBUGS-76403, which is invalid:

expected dependent Jira Issue OCPBUGS-76277 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references CORENET-6055 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.z" version, but no target version was set.

Details

In response to this:

OVN-Kubernetes is always lagging behind on the version of OVN it pins. This is causing a lot of trouble with keeping up with bug fixes and especially CVE fixes on older branches, resulting in scanners flagging this image with poor security grades and much longer time for bug fixes to be delivered to customers as the PR backporting process can take weeks or even months.

Removing the pin, so every time the new build is released in FDP, it automatically gets into versions of OpneShift that use it. There is a pre-release testing process in place between FDP and OCP QE that ensures the required test coverage before the new build is released through FDP.

Keeping OKD versions separate since sometimes new major versions are not released at the same time in FDP/RHEL and CentOS, so we may need them different at some point in time.

This PR will bring updated OVN builds and will allow picking up newer ones automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

(cherry picked from commit 3771a89)

Manual cherry pick of the change from 4.16: #2972

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

igsilya · 2026-02-09T20:04:23Z

/retest-required

igsilya · 2026-02-10T11:31:34Z

All passed on re-run. The gofmt/lint/unit jobs seem borked, and will need an override, AFAIU.

igsilya · 2026-02-11T09:58:29Z

/jira refresh

openshift-ci-robot · 2026-02-11T09:58:40Z

@igsilya: This pull request references Jira Issue OCPBUGS-76403, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.15.z) matches configured target version for branch (4.15.z)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-76277 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-76277 targets the "4.16.z" version, which is one of the valid target versions: 4.16.0, 4.16.z
bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

This pull request references CORENET-6055 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.z" version, but no target version was set.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

tssurya · 2026-03-06T12:07:10Z

/retest-required

igsilya · 2026-03-19T17:21:57Z

/retest-required

OVN-Kubernetes is always lagging behind on the version of OVN it pins. This is causing a lot of trouble with keeping up with bug fixes and especially CVE fixes on older branches, resulting in scanners flagging this image with poor security grades and much longer time for bug fixes to be delivered to customers as the PR backporting process can take weeks or even months. Removing the pin, so every time the new build is released in FDP, it automatically gets into versions of OpneShift that use it. There is a pre-release testing process in place between FDP and OCP QE that ensures the required test coverage before the new build is released through FDP. Signed-off-by: Ilya Maximets <i.maximets@ovn.org>

coderabbitai · 2026-03-20T11:16:44Z

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)

do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 81a4efa5-ed00-459a-8986-0b340ad5ab12

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

jcaamano · 2026-03-20T11:30:45Z

/lgtm
/approve
/label backport-risk-assessed

openshift-ci · 2026-03-20T11:31:28Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: igsilya, jcaamano

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~OWNERS~~ [jcaamano]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci-robot · 2026-03-20T11:43:40Z

@igsilya: This pull request references Jira Issue OCPBUGS-76403, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.15.z) matches configured target version for branch (4.15.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-76277 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-76277 targets the "4.16.z" version, which is one of the valid target versions: 4.16.0, 4.16.z
bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

This pull request references CORENET-6055 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.z" version, but no target version was set.

Details

In response to this:

OVN-Kubernetes is always lagging behind on the version of OVN it pins. This is causing a lot of trouble with keeping up with bug fixes and especially CVE fixes on older branches, resulting in scanners flagging this image with poor security grades and much longer time for bug fixes to be delivered to customers as the PR backporting process can take weeks or even months.

Removing the pin, so every time the new build is released in FDP, it automatically gets into versions of OpneShift that use it. There is a pre-release testing process in place between FDP and OCP QE that ensures the required test coverage before the new build is released through FDP.

This PR will bring updated OVN builds and will allow picking up newer ones automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

(cherry picked from commit 3771a89)

Manual cherry pick of the change from 4.16: #2972

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

igsilya · 2026-03-20T16:35:50Z

/retest-required

asood-rh · 2026-03-20T16:49:49Z

/verified by CI

e2e-aws-ovn-fdp-qe job passed

Ginkgo tests

/logs/artifacts/junit:
total 32
-rw-r--r--. 1 1012240000 1012240000 30838 Mar 20 13:25 import-SDN.xml
openshift-extended-test:
  total: 43
  failures: 0
  errors: 0
  skipped: 5

Cucushift tests

/logs/artifacts/serial/junit-report:
total 0
Done. 4 files processed.
cucushift-e2e:
  total: 25
  failures: 0
  errors: 0
  skipped: 2

openshift-ci-robot · 2026-03-20T16:50:02Z

@asood-rh: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

e2e-aws-ovn-fdp-qe job passed

Ginkgo tests

/logs/artifacts/junit:
total 32
-rw-r--r--. 1 1012240000 1012240000 30838 Mar 20 13:25 import-SDN.xml
openshift-extended-test:
 total: 43
 failures: 0
 errors: 0
 skipped: 5

Cucushift tests

/logs/artifacts/serial/junit-report:
total 0
Done. 4 files processed.
cucushift-e2e:
 total: 25
 failures: 0
 errors: 0
 skipped: 2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

igsilya · 2026-03-23T10:38:39Z

/retest-required

igsilya · 2026-03-23T20:40:13Z

/retest-required

openshift-ci-robot · 2026-03-25T10:04:39Z

/retest-required

Remaining retests: 0 against base HEAD 8fbb563 and 2 for PR HEAD 062a155 in total

pliurh · 2026-03-31T10:15:53Z

/retest-required

openshift-ci · 2026-03-31T13:43:07Z

@igsilya: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/security	`062a155`	link	false	`/test security`

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

igsilya · 2026-04-01T15:23:42Z

I see the exact same test failure on the current release-4.15 branch, so it is not related to this PR. See the example here: #3105 (https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_ovn-kubernetes/3105/pull-ci-openshift-ovn-kubernetes-release-4.15-4.15-upgrade-from-stable-4.14-local-gateway-e2e-aws-ovn-upgrade/2039306699600302080)

@pliurh @jcaamano can we just override the job for now?

pliurh · 2026-04-02T02:33:52Z

/override ci/prow/4.15-upgrade-from-stable-4.14-local-gateway-e2e-aws-ovn-upgrade

openshift-ci · 2026-04-02T02:34:03Z

@pliurh: pliurh unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers.

Details

In response to this:

/override ci/prow/4.15-upgrade-from-stable-4.14-local-gateway-e2e-aws-ovn-upgrade

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

igsilya · 2026-04-08T17:00:24Z

/test 4.15-upgrade-from-stable-4.14-local-gateway-e2e-aws-ovn-upgrade

openshift-ci-robot · 2026-04-08T20:43:22Z

@igsilya: Jira Issue Verification Checks: Jira Issue OCPBUGS-76403
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-76403 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

OVN-Kubernetes is always lagging behind on the version of OVN it pins. This is causing a lot of trouble with keeping up with bug fixes and especially CVE fixes on older branches, resulting in scanners flagging this image with poor security grades and much longer time for bug fixes to be delivered to customers as the PR backporting process can take weeks or even months.

Removing the pin, so every time the new build is released in FDP, it automatically gets into versions of OpneShift that use it. There is a pre-release testing process in place between FDP and OCP QE that ensures the required test coverage before the new build is released through FDP.

This PR will bring updated OVN builds and will allow picking up newer ones automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

(cherry picked from commit 3771a89)

Manual cherry pick of the change from 4.16: #2972

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-merge-robot · 2026-04-10T17:29:28Z

Fix included in release 4.15.0-0.nightly-2026-04-10-030227

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 9, 2026

openshift-ci Bot changed the title ~~CORENET-6055: [release-4.15] Dockerfile: Unpin OVN and consume the latest from FDP~~ OCPBUGS-76403: CORENET-6055: [release-4.15] Dockerfile: Unpin OVN and consume the latest from FDP Feb 9, 2026

openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 9, 2026

openshift-ci Bot requested review from JacobTanenbaum and abhat February 9, 2026 15:15

openshift-ci Bot changed the title ~~OCPBUGS-76403: CORENET-6055: [release-4.15] Dockerfile: Unpin OVN and consume the latest from FDP~~ OCPBUGS-76403, CORENET-6055: [release-4.15] Dockerfile: Unpin OVN and consume the latest from FDP Feb 9, 2026

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 11, 2026

openshift-ci Bot requested a review from anuragthehatter February 11, 2026 09:58

igsilya commented Mar 20, 2026

View reviewed changes

Comment thread Dockerfile.base Outdated

igsilya force-pushed the ovn-unpin-4.15 branch from 37686e1 to 062a155 Compare March 20, 2026 11:16

igsilya mentioned this pull request Mar 20, 2026

OCPBUGS-78982, CORENET-6055: [release-4.14] Dockerfile: Unpin OVN and consume the latest from FDP #3073

Merged

openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 20, 2026

openshift-ci Bot assigned asood-rh, barbora137, huiran0826, jechen0648, meinali566, mffiedler, qiowang721, rbbratta and weliang1 Mar 20, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 20, 2026

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 20, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 20, 2026

openshift-merge-bot Bot merged commit 001b26d into openshift:release-4.15 Apr 8, 2026
26 of 27 checks passed

igsilya mentioned this pull request Apr 16, 2026

[openshift-4.15] CORENET-6055: ovn-kubernetes: Remove exemptions for now unpinned OVN rpms. openshift-eng/ocp-build-data#10059

Open

Conversation

igsilya commented Feb 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Feb 9, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

igsilya commented Feb 9, 2026

Uh oh!

openshift-ci-robot commented Feb 9, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Feb 9, 2026

Uh oh!

igsilya commented Feb 9, 2026

Uh oh!

igsilya commented Feb 9, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Feb 9, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

igsilya commented Feb 9, 2026

Uh oh!

igsilya commented Feb 10, 2026

Uh oh!

igsilya commented Feb 11, 2026

Uh oh!

openshift-ci-robot commented Feb 11, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tssurya commented Mar 6, 2026

Uh oh!

igsilya commented Mar 19, 2026

Uh oh!

Uh oh!

coderabbitai Bot commented Mar 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

jcaamano commented Mar 20, 2026

Uh oh!

openshift-ci Bot commented Mar 20, 2026

Uh oh!

openshift-ci-robot commented Mar 20, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

igsilya commented Mar 20, 2026

Uh oh!

asood-rh commented Mar 20, 2026

Uh oh!

openshift-ci-robot commented Mar 20, 2026

Uh oh!

igsilya commented Mar 23, 2026

Uh oh!

igsilya commented Mar 23, 2026

Uh oh!

openshift-ci-robot commented Mar 25, 2026

Uh oh!

pliurh commented Mar 31, 2026

Uh oh!

openshift-ci Bot commented Mar 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

igsilya commented Apr 1, 2026

Uh oh!

pliurh commented Apr 2, 2026

Uh oh!

openshift-ci Bot commented Apr 2, 2026

Uh oh!

igsilya commented Apr 8, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Apr 8, 2026

Uh oh!

openshift-merge-robot commented Apr 10, 2026

Uh oh!

Reviewers

Assignees

Labels

igsilya commented Feb 9, 2026 •

edited

Loading

openshift-ci-robot commented Feb 9, 2026 •

edited by openshift-ci Bot

Loading

openshift-ci-robot commented Feb 9, 2026 •

edited by openshift-ci Bot

Loading

igsilya commented Feb 9, 2026 •

edited by openshift-ci Bot

Loading

openshift-ci-robot commented Feb 9, 2026 •

edited by openshift-ci Bot

Loading

openshift-ci-robot commented Feb 11, 2026 •

edited by openshift-ci Bot

Loading

coderabbitai Bot commented Mar 20, 2026 •

edited

Loading

openshift-ci-robot commented Mar 20, 2026 •

edited by openshift-ci Bot

Loading

openshift-ci Bot commented Mar 31, 2026 •

edited

Loading